-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NCAS Radar 1.0.0 #48
NCAS Radar 1.0.0 #48
Conversation
Some variables in CfRadial and NCAS-RADAR require variables to either be scaler (i.e. have no dimensions) or have a defined dimension, which may result in the need to check the dimensions of a scaler variable. Previously, with scaler variables having dimensions listed as "" in the output from CDLReader.to_dict() function, trying to check dimensions would say it is undefined. This change allows checking whether a variable is a scaler (defined_attrs dimension:--none--) and allows checking if a variable is a scaler or has a defined dimension (rules_attrs dimension: rule-func:match-one-of:--none--|time).
Merge changes from main into ncas-radar branch
One of the dependencies needs numpy and was allowing the release candidate of version 2 to be downloaded and installed. This then caused problems with the netCDF4 module (I think this is addressed in the next release of the netCDF module, but not the current release v1.6.5). Solution is to only allow version 1 of numpy to be installed. |
The errors on those tests are due to the CEDA API for platform checks, rather than the |
Add specs and checks needed for checking files against the NCAS-Radar standard.
A few of the bigger associated changes:
,
, this has been changed to||
. Some variables needed a rule check on their dimensions, as there were two valid options for dimensions (e.g. therange
variable could have dimensionsrange
orsweep, range
), and multiple dimensions in an option are separated by,
in the CDL representation of the file.--none--
- some variable must or could be scaler, and so a check was needed for that, but checking scaler dimensions before identified them asUNDEFINED
, as there was no value.--none--
was chosen as to represent dimensions for scaler variables as dimensions in a netCDF file can not start with a hyphen, so this is a safe value to use.string_length
. A regex check was needed to make sure there is at least one such dimension.